Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1182

reference: 206-tree-1
name: 1182
tree-preservation-order: undefined
206-tpo-1
uprn
address-text
point: POINT (-1.028902 50.866761)
geometry: MULTIPOLYGON (((-1.028845 50.866755,-1.028848 50.866766,-1.028856 50.866777,-1.028868 50.866785,-1.028884 50.866790,-1.028901 50.866792,-1.028919 50.866790,-1.028935 50.866785,-1.028948 50.866777,-1.028956 50.866767,-1.028959 50.866756,-1.028956 50.866745,-1.028948 50.866735,-1.028936 50.866727,-1.028920 50.866722,-1.028903 50.866720,-1.028885 50.866721,-1.028869 50.866726,-1.028856 50.866734,-1.028848 50.866744,-1.028845 50.866755)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL